Trigger Status

Does anyone know what the following trigger status values can be used for:

trigPreConPass
trigRunOK
trigError

I understand that they can be assigned to persistent pre-event triggers to set a return condition, but the only one that I understand is trigPreConFail, which when used stops the change that fired the trigger being made, as for these others I'm not sure, any info would be appreciated. The DXL manual gives no explanation.
SystemAdmin - Mon Sep 27 06:17:32 EDT 2010

Re: Trigger Status
llandale - Mon Sep 27 09:23:24 EDT 2010

The status only matters when the trigger code ends much like you would do with a variable designed to hold the return value of a function, when the 'return(var)' is at the bottom. So you can do this:

set(trigPreConFail)
if (some wierd conditions)
   set(trigPreConPass)

Don't understand trigRunOK and trigError, although using them overrides any fail and allows sets the trigger status to 'allow'.
This trigger allows the event:

set(trigPreConFail)
set(trigError)

Louie

Re: Trigger Status
Mathias Mamsch - Mon Sep 27 09:52:51 EDT 2010

llandale - Mon Sep 27 09:23:24 EDT 2010

The status only matters when the trigger code ends much like you would do with a variable designed to hold the return value of a function, when the 'return(var)' is at the bottom. So you can do this:

set(trigPreConFail)
if (some wierd conditions)
   set(trigPreConPass)

Don't understand trigRunOK and trigError, although using them overrides any fail and allows sets the trigger status to 'allow'.
This trigger allows the event:

set(trigPreConFail)
set(trigError)

Louie

Maybe the trigError will make the trigger stop working for subsequent calls? No idea, really... Regards, Mathias

Mathias Mamsch, IT-QBase GmbH, Consultant for Requirement Engineering and D00RS

Re: Trigger Status
llandale - Mon Sep 27 15:29:09 EDT 2010

I see that those four statuses are of type "TriggerStatus", and that the only command that uses that type is that 'set' command; you cannot 'get' the current Status.

Played with it some more. The Default status appears to be Pass (when there is no 'set' command issued in the pre-trigger).

However, I managed to play with various combinations of setPreConFail and setError, both in the trigger and in the code that deploys the trigger, and managed to change the default to Fail, most of the time. I could not reproduce what was going on and sometimes it would Pass, but I somewhat reasonably deduce that...

... Trigger statuses setError and setRunOK have something to do with default Status for future pre-triggers. e.g. perhaps sometimes "set default fail with there's a DXL Error" or "set default pass when the DXL RunOK".

But I'm spent enough time on this.

Louie

How do I find out what's defined in the Top Context?